System and method for managing and producing a dataset image across multiple storage systems

ABSTRACT

An application may store data to a dataset comprising a plurality of volumes stored on a plurality of storage systems. The application may request a dataset image of the dataset, the dataset image comprising a volume image of each volume of the dataset. A dataset image manager operates with a plurality of volume image managers in parallel to produce the dataset image, each volume image manager executing on a storage system. The plurality of volume image managers respond by performing requested operations and sending responses to the dataset image manager in parallel. Each volume image manager on a storage system may manage and produce a volume image for each volume of the dataset stored to the storage system. If a volume image for any volume of the dataset fails, or a timeout period expires, a cleanup procedure is performed to delete any successful volume images.

RELATED APPLICATION

This application claims priority to and is a continuation of U.S.application Ser. No. 13/903,745, filed on May 28, 2013, titled “SYSTEMAND METHOD FOR MANAGING AND PRODUCING A DATASET IMAGE ACROSS MULTIPLESTORAGE SYSTEMS”, which is incorporated herein.

FIELD OF THE INVENTION

Embodiments of the present disclosure relate to storage systems, and inparticular, to a system and method for managing and producing a datasetimage across multiple storage systems.

BACKGROUND

A storage system typically comprises one or more storage devices intowhich information may be entered, and from which information may beobtained, as desired. The storage system includes a storage operatingsystem that functionally organizes the system by, inter alia, invokingstorage operations in support of a storage service implemented by thesystem. The storage system may be implemented in accordance with avariety of storage architectures including, but not limited to, anetwork-attached storage environment, a storage area network and a diskassembly directly attached to a host computer. The storage devices aretypically disk drives organized as a disk array, wherein the term “disk”commonly describes a self-contained rotating magnetic media storagedevice. The term disk in this context is synonymous with hard disk drive(HDD) or direct access storage device (DASD). The storage operatingsystem of the storage system may implement a high-level module, such asa file system, to logically organize the information stored on volumesas a hierarchical structure of storage objects, such as files andlogical units (LUs). A known type of file system is a write-anywherefile system that does not overwrite data on disks.

The storage system may be further configured to allow many servers toaccess storage objects stored on the storage system. In this model, theserver may execute an application, such as a database application, that“connects” to the storage system over a computer network, such as apoint-to-point link, shared local area network (LAN), wide area network(WAN), or virtual private network (VPN) implemented over a publicnetwork such as the Internet. Each server may request the data servicesof the storage system by issuing access requests (read/write requests)as file-based and block-based protocol messages (in the form of packets)to the system over the network.

A plurality of storage systems may be interconnected as a cluster toprovide a storage system architecture configured to service manyservers. In some embodiments, the storage system architecture providesone or more aggregates, each aggregate comprising a set of one or morestorage devices (e.g., disks). Each aggregate may store one or morestorage objects, such as one or more volumes. An aggregate may bedistributed across a plurality of storage systems. The storage objects(e.g., volumes) may be configured to store content of storage objects,such as files and logical units, served by the cluster in response tomulti-protocol data access requests issued by servers.

Each storage system of the cluster may include (i) a storage server(referred to as a “D-blade”) adapted to service a particular aggregateor volume and (ii) a multi-protocol engine (referred to as an “N-blade”)adapted to redirect the data access requests to any storage server ofthe cluster. In the illustrative embodiment, the storage server of eachstorage system is embodied as a disk element (D-blade) and themulti-protocol engine is embodied as a network element (N-blade). TheN-blade receives a multi-protocol data access request from a server,converts that access request into a cluster fabric (CF) message andredirects the message to an appropriate D-blade of the cluster.

The storage systems of the cluster may be configured to communicate withone another to act collectively to increase performance or to offset anysingle storage system failure within the cluster. The cluster providesdata service to servers by providing access to a shared storage(comprising a set of storage devices). Typically, servers will connectwith a storage system of the cluster for data-access sessions with thestorage system. During a data-access session with a storage system, aserver may submit access requests (read/write requests) that arereceived and performed by the storage system.

Each server typically executes numerous applications requiring the dataservices of the cluster. For example, data for a particular applicationmay be stored as a dataset on a particular storage system of thecluster. The dataset may comprise a plurality of storage objects (e.g.,volumes) stored on the storage system. The particular application mayaccess its dataset on the storage system to add, modify, or delete dataof the dataset. In addition, the storage system may provide a backupdata service that produces a backup image of an application's dataset.The backup image of a dataset may be used for example, to restore thedataset in case of data corruption of the dataset.

In current cluster storage systems, however, it is becoming more commonfor a dataset of an application to comprise a plurality of storageobjects that are stored across a plurality of different storage systems.In this situation, it has become more difficult to produce a successfuloverall image of a dataset stored across many storage systems. Inparticular, conventionally it is difficult to coordinate and ensure thatall storage systems have successfully produced their images and have notretained stale backup images from failed backup attempts. As such, aneffective method for managing and producing an image for a datasetstored across multiple storage systems is needed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic block diagram of an exemplary cluster storagesystem environment in which some embodiments operate.

FIG. 2 is a diagram illustrating various components of the storagesystem, in accordance with some embodiments.

FIG. 3 is a schematic block diagram of an exemplary computer system, inaccordance with some embodiments.

FIG. 4 shows a conceptual diagram of a dataset image of a dataset of anapplication, the dataset comprising a plurality of volumes stored on aplurality of different storage systems.

FIGS. 5A-C are a flowchart of dataset image method for managing andproducing a dataset image of a dataset.

FIG. 6 is a flowchart of dataset image timeout method for monitoring andimplementing a dataset timeout period for producing a dataset image of adataset.

FIG. 7 shows a conceptual diagram of an exemplary configuration datastructure in accordance with some embodiments.

FIG. 8 shows a conceptual diagram of an exemplary dataset-operation datastructure in accordance with some embodiments.

FIGS. 9A-B are a flowchart of volume image method for managing andproducing one or more volume images of one or more volumes of a dataset.

FIG. 10 is a flowchart of volume image timeout method for monitoring andimplementing a dataset timeout period for producing one or more volumeimages of one or more volumes of a dataset.

FIG. 11 shows a conceptual diagram of an exemplary volume-operation datastructure in accordance with some embodiments.

FIG. 12 is a flowchart of cleanup method for deleting one or more volumeimages of one or more volumes of the dataset stored on a storage system.

DETAILED DESCRIPTION

In the following description, numerous details and alternatives are setforth for purpose of explanation. However, one of ordinary skill in theart will realize that embodiments can be practiced without the use ofthese specific details. In other instances, well-known structures anddevices are shown in block diagram form to not obscure the embodimentswith unnecessary detail.

The description that follows is divided into four sections. Section Icontains terms used herein. Section II describes a cluster storagesystem environment in which some embodiments operate. Section IIIdescribes a dataset image manager for managing and producing a datasetimage for a dataset that is stored across multiple storage systems.Section IV describes a volume image manager for managing and producingat least one volume image for at least one volume that is stored on astorage system.

I. Terms

Cluster of storage systems: As used herein, a cluster comprises aplurality of storage systems. Each storage system in the cluster may beassociated with a unique identifier (storage system ID) that uniquelyidentifies the storage system within the cluster. For example, thestorage system ID may comprise an IP address of the storage system.

Identified storage system: As used herein, an identified storage systemmay refer to a storage system that stores one or more volumes of adataset.

Storage object: As used herein, a storage object comprises any logicallydefinable storage element stored or contained within a cluster storagesystem. The cluster storage system may store a plurality of storageobjects for storing data of a plurality of applications. A storageobject may comprise any data container for storing data, such as anaggregate, volume, virtual volume (e.g., flexible volume), file, logicalunits (LUs), etc. In other embodiments, storage objects comprise anyother logically definable storage element stored or contained within thecluster storage system. For illustrative purposes, a storage objectcomprising a volume is used in the embodiments described herein. Inother embodiments, another type of storage object other than a volumemay be used in the embodiments described herein. Each storage object maybe associated with a unique storage object identifier (storage objectID) that uniquely identifies the storage object within the cluster. Forexample, each volume may be associated with a unique volume ID thatuniquely identifies the volume within the cluster.

Identified storage object: As used herein, an identified storage objectmay refer to a storage object that is included in a dataset. Forexample, an identified volume may refer to a volume that is included ina dataset.

Dataset: As used herein, a dataset may comprise data for a particularapplication. In some embodiments, a dataset comprises a plurality ofstorage objects stored on a plurality of storage systems. Theapplication may access its dataset on the storage systems to add,modify, or delete data of the dataset. For example, an emailapplication, executing on a server, may store its data to an emailexchange dataset that is stored across a plurality of storage systems.

Image: As used herein, an image may comprise a persistent point in time(PPT) view or image of data of a storage object. An image may provide aread-only copy of a storage object that protects against accidentaldeletions or modifications of data of the storage object. As such, animage may comprise a persistent image of the exact state of the data ofthe storage object at a given point in time. For example, an image maycomprise a snapshot image produced using Snapshot™ technology providedby NetApp, Inc. of Sunnyvale, Calif. In other embodiments, an image maybe produced using other technologies. An image may comprise a databackup of the storage object that may be used, for example, torestore/recover the data of the storage object after data has beencorrupted, lost, or altered. As used herein, a “storage object image”comprises an image of a storage object. As used herein, a “datasetimage” comprises an image of a dataset that comprises a plurality ofstorage objects, the dataset image comprising a plurality of storageobject images of the plurality of storage objects of the dataset. Forexample, a dataset image may comprise a plurality of volume images of aplurality of volumes of the dataset, each volume image comprising animage of one volume of the dataset.

Dataset image manager: As used herein, a dataset image manager maycomprise an application or engine configured for managing and producinga dataset image for a dataset comprising a plurality of storage objectsstored on a plurality of storage systems. The dataset image manager maymanage and produce the dataset image in response to a request from anapplication for a dataset image of its dataset. The dataset imagemanager may work in conjunction with a plurality of storage object imagemanagers (executing on a plurality of storage systems) to produce thedataset image. The dataset image manager may reside and execute on anycomputer system, such as a server system, storage system, or a dedicatedcomputer system/box.

Storage object image manager: As used herein, a storage object imagemanager may comprise an application or engine configured for managingand producing at least one storage object image for at least one storageobject stored on a storage system. The storage object image manager maymanage and produce the at least one storage object image in response toa request from the dataset image manager for the at least one storageobject image. The storage object image manager may reside and execute onthe storage system. In the exemplary embodiments described, the storageobject image manager may be referred to as a volume image manager formanaging and producing at least one volume image for at least one volumestored on a storage system.

Communication messages: Communication messages may be sent between thevarious components described herein, such as between an application, adataset image manager, and/or a volume image manager. Communicationmessages may be sent between such components, for example, through anetwork or data bus. As used herein, the following communicationmessages may be used:

Dataset-start request is sent from an application to a dataset imagemanager for beginning producing a dataset image of a dataset.

Volume-start request is sent from the dataset image manager to a volumeimage manager of each identified storage system to begin producing oneor more volume images of one or more identified volumes of the datasetstored to the storage system.

Volume-start response is sent from each volume image manager to thedataset image manager to indicate that the one or more identifiedvolumes have been suspended and producing one or more volume images ofthe one or more identified volumes has been initiated.

Dataset-start response (resume response) is sent from the dataset imagemanager to the application to indicate that all volumes of the datasethave been suspended and producing volume images of all volumes of thedataset has been initiated.

Dataset-commit request is sent from an application to the dataset imagemanager for completing producing the dataset image of the dataset.

Volume-commit request is sent from the dataset image manager to a volumeimage manager of each identified storage system to complete producingone or more volume images of one or more identified volumes of thedataset stored to the storage system. In particular, the volume-commitrequest may comprise a request for each identified storage system todetermine and indicate the success or failure of producing volume imagesof identified volumes of the dataset that are stored to the storagesystem.

Volume-commit response is sent from a volume image manager of a storagesystem to the dataset image manager to indicate the success or failureof producing volume images of identified volumes of the dataset that arestored to the storage system.

Dataset-commit response is sent from the dataset image manager to theapplication to indicate whether the dataset image of the dataset hassucceeded or failed.

Volume-cleanup request is sent from the dataset image manager to avolume image manager of each identified storage system to delete one ormore volume images of one or more volumes stored to the storage system.

II. Cluster Storage System Environment

FIG. 1 is a schematic block diagram of an exemplary cluster storagesystem environment 100 in which some embodiments operate. Theenvironment 100 comprises one or more server systems 110 (such as 110 a,110 b, 110 c, etc.) and a plurality of storage systems 120 (such as 120a, 120 b, 120 c, etc.) connected via a connection system 130. Theplurality of storage systems 120 comprises a cluster storage system 115.Each storage system 120 comprises a set of one or more storage devices125 (such as 125 a, 125 b, 125 c, etc.). The connection system 130 maycomprise a network, such as a Local Area Network (LAN), Wide AreaNetwork (WAN), metropolitan area network (MAN), the Internet, or anyother type of network or communication system between computer systems.

Each storage system 120 may have a distributed architecture. Forexample, each storage system 120 may include separate N module (networkmodule) and D module (data module) components (not shown). In such anembodiment, the N module is used to communicate with the server systems110, while the D module includes the file system functionality and isused to communicate with the storage devices 125. In another embodiment,the storage system may have an integrated architecture, where thenetwork and data components are all contained in a single box or unit.The storage system 120 may be coupled through a switching fabric (notshown) to other storage systems 120 in the cluster 115. In this way, allthe storage systems 120 of the cluster 115 may be interconnect to form asingle storage pool that may be accessed by the connected server systems110.

The storage systems 120 comprise functional components that cooperate toprovide a distributed storage system architecture providing consolidateddata services to the server systems 110. A server system 110 maycomprise a computer system that utilizes services of the cluster storagesystem 115 to store and manage data in the storage devices 125 of thestorage systems 120. Interaction between a server system 110 and astorage system 120 can enable the provision of storage services. Thatis, server system 110 may request the services of the storage system120, and the storage system 120 may return the results of the servicesrequested by the server system 110, by exchanging packets over theconnection system 130. The server system 110 may request the services ofthe storage system by issuing packets using file-based access protocols,such as the Common Internet File System (CIFS) protocol or Network FileSystem (NFS) protocol, over the Transmission Control Protocol/InternetProtocol (TCP/IP) when accessing information in the form of files anddirectories. Alternatively, the server system 110 may issue packetsincluding block-based access protocols, such as the Fibre ChannelProtocol (FCP), or Internet Small Computer System Interface (iSCSI)Storage Area Network (SAN) access, when accessing information in theform of blocks.

The storage system 120 may comprise a computer system that stores datain a set of storage devices 125, preferably on one or more writablestorage device media (such as magnetic disks, video tape, optical, DVD,magnetic tape, and any other similar media adapted to store information,including data and parity information). The storage system 120 mayimplement a file system to logically organize the data as storageobjects on the storage devices 125. A server system 110 may execute oneor more applications that submit access requests for accessingparticular storage objects on the storage devices 125.

FIG. 2 is a diagram illustrating various components of a storage system120, in accordance with some embodiments. Specifically, the storagesystem comprises one or more processors 222, a memory 224, a networkadapter 225, and a storage adapter 228 interconnected by a system bus223. The storage system 120 executes a storage operating system 230 thatimplements a storage file system. The memory 224 comprises storagelocations that are addressable by the processors 222 and adapters 225and 228 for storing software program code (such as the storage operatingsystem 230 and volume image manager 250) and data structures. Theprocessor and adapters may, in turn, comprise processing elements and/orlogic circuitry configured to execute the software code and manipulatevarious data.

The network adapter 225 comprises a plurality of ports adapted to couplethe storage system 120 to one or more server systems 110 overpoint-to-point links, wide area networks, virtual private networksimplemented over a public network (Internet) or a shared local areanetwork. A server system 110 may establish a connection with a storagesystem 120 through the network adapter 225 to access the storage devices125 of the storage system (through use of the storage adapter 228). Insome embodiments, an application executing on the server system 110 mayestablish a connection with a storage system 120 to access the storagedevices 125.

The storage adapter 228 is coupled with the storage devices 125 of thestorage system and cooperates with the storage operating system 230 toaccess particular data on the storage devices 125 (e.g., as requested byan application executing on the server system 110). The storage adapter228 comprises a plurality of ports having input/output (I/O) interfacecircuitry that couples to the storage devices 125 over an I/Ointerconnect arrangement. The storage operating system 230, portions ofwhich are typically resident in memory 224 and executed by theprocessing elements, functionally organizes the storage system 120 by,inter alia, invoking storage operations in support of the storageservice implemented by the storage system 120. It will be apparent tothose skilled in the art that other processing and memory means,including various computer readable media, may be used for storing andexecuting program instructions pertaining to the invention describedherein.

The storage system 120 executes a storage operating system 230 thatimplements a storage file system. In this sense, the Data ONTAP® storageoperating system, available from NetApp, Inc. of Sunnyvale, Calif., thatimplements a Write Anywhere File Layout (WAFL®) file system, is anexample of such a storage operating system implemented as a microkernelwithin an overall protocol stack and associated storage. The storageoperating system 230 can also be implemented as an application programoperating over a general-purpose operating system, such as UNIX® orWindows®, or as a general-purpose operating system with configurablefunctionality, which is configured for storage applications as describedherein.

The memory 224 may store software program code such as the storageoperating system 230 that is executable by the processor(s) 222. Thestorage operating system 230 may implement the storage file system tologically organize data on the storage devices 125 as one or morestorage objects and provide a logical/virtual representation of how thestorage objects are organized on the storage devices 125. As such, acluster of one or more storage systems 120 may also organize and storeone or more storage objects. As used herein, a storage object comprisesany logically definable storage element stored or contained within thecluster storage system 115. Each storage object may be associated with aunique storage object identifier (storage object ID) that uniquelyidentifies the storage object within the cluster 115. For example, eachvolume may be associated with a unique volume ID that uniquelyidentifies the volume within the cluster. The storage operating system230 of a storage system 120 also manages access to the storage objectsstored on the storage devices 125. In some embodiments, an applicationmay establish a connection with the storage operating system 230 toaccess storage devices 125 of the storage system 120. The applicationmay implement various connections having various protocols to establisha connection with the storage system 120, such as an iSCSI or aTransport Control Protocol (TCP) connection.

In some embodiments, each storage system 120 in the cluster may executea volume image manager 250. In these embodiments, the memory 224 mayalso store software program code such as the volume image manager 250that is executable by the processor(s) 222. In this manner, the volumeimage manager 250 may comprise a volume image manager engine 250comprising computer software and/or hardware components configured forperforming embodiments described herein. The volume image manager 250may be configured for managing and producing at least one volume imagefor at least one volume stored on the storage system. The volume imagemanager 250 may perform embodiments described herein in response torequest(s) from a dataset image manager 350. In some embodiments, thememory 224 may also store data structures (such as a volume-operationdata structure 1100) that are used by the volume image manager 250 forperforming embodiments described herein.

FIG. 3 is a schematic block diagram of an exemplary computer system 300,in accordance with some embodiments. The computer system 300 may executea dataset image manager 350. In some embodiments, the computer system300 may comprise a server system 110, a storage system 120, or adedicated computer system/box for executing the dataset image manager350. In these embodiments, the dataset image manager 350 may reside andexecute on any computer system, such as a server system 110, a storagesystem 120, or a dedicated computer system/box. In some embodiments, thedataset image manager 350 resides on each storage system 120. In theseembodiments, when an application interacts with a particular storagesystem 120 to initiate producing a dataset image, the dataset imagemanager 350 residing on that particular storage system 120 may initiateand manage operations for producing the dataset, as described herein.

The computer system 300 comprises processor(s) 326, memory 328, a localstorage 392, a network adapter 395, output component(s) 397, and inputcomponent(s) 398 coupled by a bus 346. The processors 326 are thecentral processing units (CPUs) of the computer system 300 and, thus,control the overall operation of the computer system 300. Processors 326may include one or more programmable general-purpose or special-purposemicroprocessors, digital signal processors (DSPs), programmablecontrollers, application specific integrated circuits (ASICs),programmable logic devices (PLDs), or the like, or a combination of suchdevices. The network adapter 395 comprises a plurality of ports adaptedto couple the computer system 300 to one or more other computer systems(such as servers or storage systems 120) over point-to-point links, widearea networks, virtual private networks implemented over a publicnetwork (Internet) or a shared local area network. The network adapter395 thus may comprise the mechanical, electrical and signaling circuitryneeded to connect the storage system to the network.

The output component(s) 397 may be of any type generally used by acomputer system to provide information to an end user (e.g.,administrator). For example, the output component 397 could include amonitor, an audio speaker, or an alphanumeric display. Similarly, theinput component(s) 398 may be of any type that allows an end user toprovide input into a computer system. For example, the input component398 may be a keyboard, a mouse, or a speech recognition system.

Memory 328 can be a random access memory (RAM), a read-only memory(ROM), or the like, or a combination of such devices. It will beapparent to those skilled in the art that other processing and memorymeans, including various computer readable media, may be used forstoring and executing program instructions pertaining to the embodimentsdescribed herein. Memory 328 comprises storage locations that areaddressable by the processor 326 and adapters for storing softwareprogram code, such as software described herein. The processor 326 andadapters may, in turn, comprise processing elements and/or logiccircuitry configured to execute the software code. Such software codemay include an operation system (not shown) and one or more applications330.

In some embodiments, an application 330 stores its data to a dataset.The dataset may comprise a plurality of storage objects stored on aplurality of different storage systems 120. The application may accessits dataset on the storage systems to add, modify, or delete data of thedataset. For example, an email application 330, executing on thecomputer system 300, may store its data to an email exchange datasetthat is stored across a plurality of different storage systems 120. Thecomputer system 300 may also execute a dataset image manager 350.

In these embodiments, the memory 328 may also store software programcode such as the dataset image manager 350 that is executable by theprocessor(s) 326. In this manner, the dataset image manager 350 maycomprise a dataset image manager engine 350 comprising computer softwareand/or hardware components configured for performing embodimentsdescribed herein. The dataset image manager 350 may be configured formanaging and producing a dataset image for a dataset. The dataset imagemanager 350 may manage and produce the dataset image in response to arequest from an application 330 for a dataset image of its dataset. Thedataset image manager 350 may work in conjunction with a plurality ofvolume image managers 250 (executing on a plurality of storage systems120) to produce the dataset image. In some embodiments, the memory 328may also store data structures such as a configuration data structure(DS) 700 and an dataset-operation data structure (DS) 800 that are usedby the dataset image manager 350 for performing embodiments describedherein. In other embodiments, the dataset image manager 350 may resideand execute on a storage system 120.

Local storage 392 is a storage device that stores data structures suchthe configuration DS 700 and the dataset-operation DS 800 that are usedby the dataset image manager 350 for performing embodiments describedherein. The computer system 300 may load data stored on the localstorage 392 into memory 328 from which they are accessed by processors326.

III. Dataset Image Manager for Managing and Producing a Dataset Image A.Overview of Dataset Image Manager and Volume Image Manager

As described herein, an application may store its data to a datasetcomprising a plurality of volumes stored on a plurality of storagesystems. The application may require a backup image (dataset image) ofthe dataset. A resulting produced dataset image may comprise a pluralityof volume images stored on a plurality of storage systems. In someembodiments, the dataset image manager 350 operates in conjunction witha plurality of volume image managers 250, each volume image manager 250residing and executing on a storage system among the plurality ofstorage systems.

In particular, the dataset image manager 350 may manage and coordinateoperations for the plurality of volume image managers 250 by sendingrequests to the plurality of volume image managers 250 for producing thedataset image. In some embodiments, the dataset image manager 350 mayperform interactions and operations between the plurality of volumeimage managers 250 in parallel. The plurality of volume image managers250 may also respond by performing requested operations and sendingresponses to the dataset image manager 350 in parallel. Each volumeimage manager 250 executing on a storage system may manage at least onevolume image for at least one identified volume of the dataset that isstored to the storage system. The dataset image manager 350 may storeand maintain a dataset-operation DS 800 to perform embodiments herein.The volume image manager 250 may store and maintain a volume-operationDS 1100 to perform embodiments herein.

The dataset image manager 350 may execute a dataset image method 500(described in relation to FIGS. 5A-C) for managing and producing thedataset image. In some embodiments, the dataset image method 500 may beviewed as comprising two phases for producing a dataset image of adataset: a start phase and a commit phase. The start phase generallyrelates to suspending all volumes of the dataset and initiate/beginproducing a dataset image of its dataset. The commit phase generallyrelates to managing and completing the volume images of the volumes ofthe dataset to produce the dataset image. Typically, the start phaserequires a substantially shorter time to complete relative to the commitphase. Dividing the dataset image method 500 may provide performance andscalability advantages. For example, in the start phase, the datasetimage manager 350 may receive a dataset-start request from anapplication for beginning producing a dataset image of a dataset of theapplication and the dataset image manager 350 will coordinate with theplurality of volume image managers 250 to quickly suspend/fence allvolumes of the dataset (i.e., suspend all input/output (I/O) operationsof all volumes of the dataset). After all volumes of the dataset aresuspended, the dataset image manager 350 may send a resumeresponse/signal to the application. Typically, each application will beconfigured such that it will not resume its other operations (operationsnot related to I/O operations to the volumes of its dataset) until itreceives the resume response. As such, by dividing the dataset imagemethod 500 into a start phase and a commit phase, the application doesnot need to wait for the substantially longer commit phase to completebefore receiving the resume response and resuming its other operations.This may be especially important for database and other applicationsthat are sensitive to performance latency.

Each volume image manager 250 may execute a volume image method 900(described in relation to FIGS. 9A-B) for managing and producing one ormore volume images. The dataset image method 500 may manage andcoordinate operations and requests for the volume image method 900, andvolume image method 900 may respond by performing the requests. As such,the volume image method 900 may also be viewed as comprising a startphase and a commit phase for managing and producing one or more volumeimages.

In some embodiments, producing a dataset image for a dataset isconsidered successful only if a volume image is successfully producedfor each and all volumes of the dataset across the plurality of storagesystems within a predetermined timeout period. In these embodiments, ifeven one volume image manager 250 on a storage system does notsuccessfully produce a volume image for even one volume of the dataset,producing the dataset image is considered a failure.

Also, if all volume images of all volumes of the dataset are notsuccessfully produced within the timeout period, producing the datasetimage is also considered a failure. In some embodiments, either thedataset image manager 350 and/or any of the volume image managers 250may enforce the timeout period and cause a failure of the dataset image.In these embodiments, the dataset image manager 350 may initiate adataset image timeout method 600 (described in relation to FIG. 6) thatis executed for monitoring and implementing the timeout period. Also,each volume image manager 250 may separately and individually monitorand implement the timeout period by initiating a volume image timeoutmethod 1000 (described in relation to FIG. 10).

As such, the producing the dataset image may fail if producing one ormore volume images fails, or the timeout period expires before theentire dataset image is produced. When producing the dataset image fails(either by a failed volume image or expiration of the timeout period), acleanup procedure is performed to delete one or more volume imagesproduced and stored on one or more storage systems. In some embodiments,the cleanup procedure may be used for deleting one or more volume imagesthat were successfully produced on one or more storage systems. Sincethe volume images were produced for an unsuccessful data image, thevolume images are no longer needed and unnecessarily consumes storageresources. As such, the cleanup procedure provides automated removal ofunneeded volume images that were produced for an unsuccessful dataimage. The dataset image manager 350 may initiate a cleanup procedureacross the plurality of storage systems, wherein in response, eachvolume image manager 350 on each storage system executes a cleanupmethod 1200 (as described in relation to FIG. 12). In addition, eachvolume image manager 350 of each storage system may also separately andindividually initiate a cleanup procedure on the storage system.

As such, the embodiments described herein provide a system and methodfor providing an ability to create crash consistent multi-volume image.The system and method may do so by suspending I/O operations to thevolumes during the duration of image creation for the volumes.

B. Dataset Image

FIG. 4 shows a conceptual diagram of a dataset image of a dataset of anapplication, the dataset comprising a plurality of volumes stored on aplurality of different storage systems 120. In some embodiments, thedataset comprises at least one volume from each of at least twodifferent storage systems 120. For example, as shown in FIG. 4, thedataset may comprise at least one volume 405 a stored on a first storagesystem 120 a, at least one volume 405 b stored on a second storagesystem 120 b, at least one volume 405 c stored on a third storage system120 c, etc.

As shown in FIG. 4, the dataset image manager 350 may manage andcoordinate with a plurality of volume image managers 250 (e.g., 250 a,250 b, 250 c) executing on the plurality of storage system 120 (e.g.,120 a, 120 b, 120 c) for performing embodiments herein for producing adataset image 425. In some embodiments, each volume image manager 250executing on a storage system 120 may manage and produce at least onevolume image 410 for the at least one identified volume 405 of thedataset that is stored to the storage system 120. As used herein, for aparticular storage system 120, an identified volume may refer to avolume of a dataset that is stored to the particular storage system 120.For example, as shown in FIG. 4, a first volume image manager 250 a mayproduce at least one volume image 410 a for at least one volume 405 a ofthe dataset that is stored on a first storage system 120 a, a secondvolume image manager 250 b may produce at least one volume image 410 bfor at least one volume 405 b of the dataset that is stored on a secondstorage system 120 b, a third volume image manager 250 c may produce atleast one volume image 410 c for at least one volume 405 c of thedataset that is stored on a third storage system 120 c, etc.

A dataset image 425 may comprise a plurality of volume images 410 of aplurality of volumes 405 that are stored on a plurality of differentstorage systems 120. In some embodiments, the dataset image 425comprises at least one volume image 410 for at least one volume 405 fromeach of at least two different storage systems 120. For example, asshown in FIG. 4, the dataset image 425 may comprise at least one volumeimage 410 a for at least one volume 405 a stored on a first storagesystem 120 a, at least one volume image 410 b for at least one volume405 b stored on a second storage system 120 b, at least one volume image410 c for at least one volume 405 c stored on a third storage system 120c, etc.

C. Method for Managing and Producing a Dataset Image

FIGS. 5A-C are a flowchart of dataset image method 500 for managing andproducing a dataset image of a dataset. In some embodiments, the datasetcomprises a plurality of storage objects (e.g., volumes) stored on aplurality of different storage systems 120. Steps of method 500 may beperformed by various hardware and/or software components residing andexecuting on a computer system 300 and/or storage system 120 that areconfigured for performing the method 500. In some embodiments, some orall steps of the method 500 are performed by a dataset image manager 350residing and executing on a computer system 300 (such as a server system110 or storage system 120). The method 500 may use various communicationmessages sent between the various components described herein, such asbetween an application, a dataset image manager, and/or a volume imagemanager. Communication messages may be sent between such components, forexample, through a network, data bus, or the like. The order and numberof steps of the method 500 are for illustrative purposes only and, inother embodiments, a different order and/or number of steps are used.

In general, the dataset image method 500 may determine the plurality ofvolumes that comprise a dataset, as well as determine the plurality ofstorage systems 120 that store the plurality of volumes. The datasetimage method 500 may then manage and produce a dataset image of thedataset by coordinating with a plurality of volume image managers 250executing on the plurality of storage systems 120. In some embodiments,the dataset image method 500 may perform interactions and operationsbetween the plurality of volume image managers 250 in parallel. Theplurality of volume image managers 250 may also respond by performingrequested operations and sending responses to the dataset image manager350 in parallel. In these embodiments, the plurality of volume imagemanagers 250 may perform operations described herein simultaneously formanaging and producing the volume images in parallel to allow for fasterexecution of the dataset image method 500 and production of the datasetimage across the plurality of storage systems 120. In addition, thedataset image method 500 may initiate a dataset image timeout method 600(described in relation to FIG. 6) that is simultaneously executed formonitoring and implementing a dataset timeout period that may cause anabort/stoppage of the dataset image method 500.

The method 500 begins by storing and maintaining (at 510) aconfiguration data structure for storing configuration information for aplurality of volumes stored on a plurality of storage systems 120 of acluster storage system 115. FIG. 7 shows a conceptual diagram of anexemplary configuration data structure 700 in accordance with someembodiments. The configuration data structure 700 may comprise aplurality of volume entries 701 (such as 701 a, 701 b, etc.), eachvolume entry 701 representing a volume stored in the cluster storagesystem 115. Each volume entry 701 for a volume may comprise a pluralityof data fields, such as data fields for a volume ID 705 (e.g., VID1,VID2, etc.), storage system ID 710 (e.g., SSID1, SSID2, etc.), andvolume information 715 (e.g., VI1, VI2, etc.).

As discussed above, each volume may be associated with a unique volumeID 705 that uniquely identifies the volume within the cluster. Also,each storage system 120 in the cluster may be associated with a uniquestorage system ID 710 that uniquely identifies the storage system 120within the cluster. For example, the storage system ID may comprise anIP address of the storage system. As such, for a particular volume thatis represented by a particular volume entry 701, the data field for thevolume ID 705 may specify a volume ID associated with the particularvolume and the data field for the storage system ID 710 may specify astorage system ID of the storage system that stores the particularvolume. Also, the data field for the volume information 715 may specifyvarious information regarding the particular volume. For example, thevolume information 715 may include a data size of the volume, dates andtimes when the volume was created, accessed, or modified, dates andtimes when any data images were produced for the volume, etc. In otherembodiments, the volume information 715 may include other informationregarding the volume. In some embodiments, the configuration datastructure 700 may be used by the method 500 as a look-up or mappingtable to determine which storage system 120 stores a particular volume.

The method 500 then receives (at 515) a dataset-start request, from anapplication (such as an application 330 executing on a computer system300) for beginning producing a dataset image of a dataset. For example,the dataset-start request may comprise a dataset-start applicationprogramming interface (API) call from the application. In someembodiments, the dataset-start request further specifies a plurality ofvolumes that comprise the dataset. For example, the dataset-startrequest may specify a plurality of volume IDs of the plurality ofvolumes that comprise the dataset. In these embodiments, the pluralityof volumes that comprise the dataset are stored across a plurality ofdifferent storage systems 120. For example, the application may comprisean email application that stores its data to an email exchange datasetcomprising a plurality of volumes stored on a plurality of storagesystems 120. The application will typically not have knowledge orinformation regarding which storage systems 120 store the volumes of thedataset, and as such, the dataset-start request will typically notspecify the storage systems 120 storing the dataset. In someembodiments, receiving the dataset-start request initiates the startphase of the method 500.

The method 500 then determines (at 520) a start time and dataset timeoutperiod for the overall dataset image operation. The start time maycomprise the start time for the overall dataset image operation forproducing the dataset image of the dataset. For example, the start timemay comprise a time (or approximate time) when the method 500 receivedthe dataset-start request from the application. The dataset timeoutperiod may comprise a maximum amount of time that is allowed/permittedfor the overall dataset image operation to produce the dataset imagebefore the overall dataset image operation is stopped/aborted. Thedataset timeout period may be defined by and start from the start time.Different values may be used for the dataset timeout period depending ondifferent situations. For example, for urgent situations where a datasetimage is needed quickly, the dataset timeout period may equal 5 secondsfrom the start time, for average situations where a dataset image isneeded in an average time, the dataset timeout period may equal 7seconds from the start time, and for relaxed situations where a datasetimage is not needed quickly, the dataset timeout period may equal 20seconds from the start time. In other embodiments, other values for thetime period may be used. In other embodiments, the value for the timeperiod may be user specified.

In some embodiments, the dataset timeout period may be enforced by thedataset image manager 350 and/or a volume image manager 250 executing onany storage system 120. The dataset image manager 350 may implement adataset image timeout method 600 (discussed in relation to FIG. 6) toenforce the dataset timeout period on the plurality of storage systemsstoring the dataset. If the dataset timeout period expires, the datasetimage manager 350 may cause the dataset image method 500 for producingthe dataset image to stop/abort, as well as initiate an image cleanupprocedure on the plurality of storage systems storing the dataset. Inaddition, each volume image manager 250 may execute a volume imagemethod 900 (discussed in relation to FIG. 9) for producing volume imagesof volumes of a dataset and implement a volume image timeout method 1000(discussed in relation to FIG. 10) to enforce the dataset timeout periodon the particular storage system on which the volume image manager 250executes and resides. If the dataset timeout period expires, the volumeimage manager 250 may cause the volume image method 900 to stop/abort,as well as initiate an image cleanup procedure on the particular storagesystem.

The method 500 then identifies (at 525) the plurality of storage systemsthat store the plurality of volumes that comprise the dataset. Forexample, the method 500 may determine a plurality of storage system IDsof the plurality of storage systems that store the dataset. As usedherein, an “identified storage system” may refer to a storage systemthat stores one or more volumes of the dataset. Note that the method mayreceive (at 510) a dataset-start request specifying a plurality ofvolume IDs of the plurality of volumes that comprise the dataset, butthe dataset-start request will typically not specify the storage systems120 storing the dataset. In some embodiments, the method 500 identifiesthe plurality of storage systems that store the dataset by using theconfiguration data structure 700 as a look-up or mapping table. Forexample, for each volume ID 705 of a volume specified in thedataset-start request, the method 500 may determine a matching entry 701in the configuration data structure 700 having a matching volume ID 705and identify the storage system ID 710 in the matching entry 701 as thestorage system that stores the volume. In this manner, the method 500may identify a plurality of storage system IDs of the plurality ofstorage systems that store the dataset.

The method 500 then produces (at 530) a plurality of groupings(sometimes referred to as buckets) for the plurality of volumes of thedataset. For example, each grouping/bucket may comprise all volumes ofthe dataset that are stored on a same storage system. In this manner,each grouping may represent a single storage system, the groupingcomprising one or more volumes of the dataset that are stored on thesingle storage system. As such, the method 500 organizes and divides (at530) the plurality of volumes of the dataset into a plurality ofgroupings.

The method 500 then produces (at 535) a new operation ID (also referredto as a token ID) for producing the dataset image. The operation ID mayrepresent an overall dataset image operation for producing the entiredataset image for the dataset. The overall dataset image operation maycomprise sub-operations for producing the various volume images for thevolumes comprising the dataset. The operation ID may comprise a uniqueidentifier that uniquely identifies the overall operation for producingthe dataset image among other possible overall operations for producingother dataset images of other datasets. In general, the operation ID maybe specified in communications between the application, the datasetimage manager 350, and/or the plurality of volume image managers 250 touniquely identify the overall dataset image operation that thecommunication pertains to.

The method 500 then produces (at 540) a new dataset-operation datastructure (DS) 800 corresponding to and being associated with the newoperation ID, and stores various data/information needed for managingand producing the dataset image to the dataset-operation DS 800. Forexample, the method 500 may store the data/information determined insteps 520 through 535 to the dataset-operation DS 800. Such data mayinclude the operation ID, start time, and dataset timeout period for theoverall dataset image operation, the plurality of storage system IDs ofthe plurality of storage systems that store the dataset, and/or theplurality of groupings. The data/information used for managing andproducing the dataset image may be organized and stored in thedataset-operation DS 800 in various manners using any organizationalstructure.

FIG. 8 shows a conceptual diagram of an exemplary dataset-operation DS800 in accordance with some embodiments. The dataset-operation DS 800may comprise a plurality of grouping entries 801 (such as 801 a, 801 b,etc.) and a header 805. The header 805 may comprise data fields for anoperation ID 810, start time 815, and/or dataset timeout period 820.Each grouping entry 801 represents a grouping and a single storagesystem, the grouping comprising one or more volumes of the dataset thatare stored on the single storage system. Each grouping entry 801 for astorage system may comprise a plurality of data fields, such as datafields for a storage system ID 850 (e.g., SSID1) of the storage system,one or more volume IDs 855 (e.g., VID1, VID2, etc.) of one or morevolumes of the dataset that are stored on the storage system, and aplurality of indicators/flags (such as volume-start response 860 andvolume-commit response 865).

In the exemplary dataset-operation DS 800 of FIG. 8, the datasetcomprises a plurality of volumes VID1, VID3, VID4, VID11, VID13, whereinvolume VID1 is stored on a first storage system SSID1, volumes VID3 andVID4 are stored on a second storage system SSID2, and volumes VID11 andVID13 are stored on a third storage system SSID3. As such, a firstgrouping and a first grouping entry 801 a is produced to represent thefirst storage system, the first grouping entry 801 a specifying thestorage system ID SSID1 850 and the volume ID VID1 855; a secondgrouping and a second grouping entry 801 b is produced to represent thesecond storage system, the second grouping entry 801 b specifying thestorage system ID SSID2 850 and the volume IDs VID3 and VID4 855; and athird grouping and a third grouping entry 801 c is produced to representthe third storage system, the third grouping entry 801 c specifying thestorage system ID SSID3 850 and the volume IDs VID11 and VID13 855.

The method 500 then calls/initiates (at 545) the dataset image timeoutmethod 600. The dataset image timeout method 600 may have access to thedataset-operation DS 800 and determine the start time and datasettimeout period. Using the start time and dataset timeout period from thedataset-operation DS 800, the dataset image timeout method 600 mayimplement/enforce the dataset timeout period on the method 500 forproducing the dataset image (as discussed in relation to FIG. 6).

The method 500 then sends (at 550) a volume-start request to the volumeimage manager 250 of each identified storage system 120 for suspendingone or more volumes of the dataset and begin producing volume images ofone or more volumes of the dataset. The method 500 may identify whichstorage systems 120 to send the volume-start request using thedataset-operation DS 800, wherein the method 500 may identify/selecteach storage system specified in the storage system ID 850 data field.The volume-start request may comprise a volume-start applicationprogramming interface (API) call from the dataset image manager 350 tothe volume image manager 250 of each identified storage system 120.

The volume-start request sent to an identified storage system 120 mayspecify all volumes or at least one volume of the dataset (e.g., specifyall volume IDs or at least one volume ID of the dataset). In someembodiments, the volume-start request specifies all volumes of thedataset, whereby the volume image manager 250 of each identified storagesystem 120 determines which particular volumes of the dataset are storedto its particular storage system 120. In other embodiments, thevolume-start request sent to an identified storage system 120 mayspecify only those volumes of the dataset that are stored on theidentified storage system 120. In these embodiments, the method 500 mayuse the dataset-operation DS 800 to produce the volume-start request foreach identified storage system 120 to specify only those volumes listedin the volume ID 855 data field. As such, in these embodiments, themethod 500 may produce and send (at 550) a plurality of differentvolume-start requests to a plurality of identified storage systems 120,each volume-start request being customized/adapted to each particularidentified storage system 120.

In some embodiments, each volume-start request further specifies theoperation ID 810, the start time 815, and the dataset timeout period820. The operation ID may be used in interactions and communicationsbetween the dataset image manager 350 and each volume image manager 250to uniquely identify the overall dataset image operation. The start time815 and the dataset timeout period 820 may be used by each volume imagemanager 250 to individually and separately enforce the dataset timeoutperiod.

In some embodiments, the volume image manager 250 of each storage system120 maintains a volume-operation data structure (DS) for storing variousdata/information for managing and producing one or more volume images ofone or more volumes of a particular dataset. For example, thevolume-operation DS may store the operation ID, the start time, and thedataset timeout period associated with the particular dataset. Inaddition, the volume-operation DS (DS) may store volume IDs of one ormore volumes of the particular dataset that are stored on the storagesystem 120. In this manner, the operation ID may be used by the volumeimage manager 250 to identify an overall dataset image operation and itscorresponding volume-operation DS storing the various data/informationfor the overall dataset image operation.

In some embodiments, the dataset image method 500 may performinteractions and operations between the plurality of volume imagemanagers 250 in parallel. In these embodiments, the method 500 may send(at 550) the plurality of volume-start requests to the plurality ofidentified storage systems 120 simultaneously and in parallel to allowfor faster execution of the dataset image method 500.

In some embodiments, the volume-start request sent to an identifiedstorage system 120 comprises a request to suspend and initiate/beginproducing volume images of all volumes of the dataset that are stored onthe identified storage system 120. When a storage system 120 hassuccessfully completed suspending all volumes of the dataset stored onthe storage system 120 and initiated producing the volume images of allvolumes of the dataset stored on the storage system 120, the volumeimage manager 250 on the storage system 120 may send a volume-startresponse to the dataset image manager 350. The volume-start response maycomprise the operation ID of the overall dataset image operation thatthe response pertains to.

The method 500 then determines (at 555) that a volume-start response hasbeen received from each identified storage system 120 that stores one ormore volumes of the dataset. A volume-start response from a storagesystem 120 indicates that all volumes of the dataset stored on thestorage system 120 have been suspended and producing the volume imagesof the volumes has been initiated (which is different than an indicationthat the volume images of the volumes have been completed). The method500 may determine step 555 by using the dataset-operation DS 800associated with the specified operation ID. For example, when avolume-start response is received from a storage system, the method 500may indicate such in the grouping entry 801 for the storage system. Inthe exemplary dataset-operation DS 800 of FIG. 8, a volume-startresponse 860 data field in each grouping entry 801 indicates whether ornot a volume-start response has been received from the storage system.When the method 500 determines that all grouping entries 801 in thedataset-operation DS 800 have a volume-start response 860 data fieldindicating that a volume-start response has been received, the method500 may determine (at 555) that a volume-start response has beenreceived from each identified storage system 120, and thus all volumesof the dataset have successfully been suspended.

The method 500 then sends (at 560) a dataset-start response to theapplication indicating that all volumes of the dataset are suspended andvolume images of all volumes of the dataset has been initiated. Thedataset-start response may comprise a response to the dataset-startrequest received (at 515) from the application. The dataset-startresponse is sometimes referred to as a resume response. The resumeresponse further specifies the operation ID of the overall dataset imageoperation that the response pertains to. The application will beconfigured such that, after receiving the dataset-start request, itresumes its other operations (operations not related to I/O operationsto the volumes of its dataset) only after it receives the resumeresponse. As such, by dividing the dataset image method 500 into a startphase and a commit phase, the application receives the resume responseafter the shorter start phase and may quickly resume its otheroperations. In addition to resuming its other operations, theapplication will also be configured to send a data-set commit request tothe dataset image manager 350 in response to receiving the resumeresponse.

As such, the method 500 then receives (at 565) a dataset-commit requestfrom the application for managing and completing the dataset image. Forexample, the dataset-commit request may comprise a dataset-commitapplication programming interface (API) call from the application. Thedataset-commit request further specifies the operation ID of the overalldataset image operation that the request pertains to. In someembodiments, receiving the dataset-commit request (at 565) initiates thecommit phase of the method 500.

The method 500 then sends (at 570) a volume-commit request to the volumeimage manager 250 of each identified storage system 120 that stores oneor more volumes of the dataset for completing volume images of the oneor more volumes and for unsuspending/restarting I/O operations onvolumes of the dataset. Each volume image manager, after receiving thevolume-commit request, ensures to completing any ongoing volume imagesand then it unsuspends/restarts the I/O operations immediately. With thevolume-commit request, the method 500 also queries each volume imagemanager if the volume images on the storage system were successful ornot. The method 500 may identify which storage systems 120 to send thevolume-commit request by using the dataset-operation DS 800corresponding to the operation ID specified in the receiveddataset-commit request. Using the corresponding dataset-operation DS800, the method 500 may identify/select each storage system specified inthe storage system ID 850 data field. The volume-commit request maycomprise a volume-commit application programming interface (API) callfrom the dataset image manager 350 to the volume image manager 250 ofeach identified storage system 120. Each volume-commit request mayfurther specify the operation ID that the request pertains to. Using theoperation ID, the volume image manager 250 of each identified storagesystem 120 may identify the corresponding volume-operation DS anddetermine the volume IDs of those volumes the volume-commit requestpertains to (i.e., the volumes of the dataset that are stored to thestorage system 120).

In some embodiments, the dataset image method 500 may performinteractions and operations between the plurality of volume imagemanagers 250 in parallel. In these embodiments, the method 500 may send(at 570) the plurality of volume-commit requests to the plurality ofidentified storage systems 120 simultaneously and in parallel to allowfor faster execution of the dataset image method 500.

In particular, the volume-commit request may comprise a request for eachidentified storage system 120 to determine and indicate the success orfailure of producing volume images of each and all volumes of thedataset that are stored to the storage system 120. When the volume imagemanager 250 of each identified storage system 120 determines whetherproducing volume images of volumes of the dataset that are stored to thestorage system 120 is a success or failure, the volume image manager 250sends a volume-commit response to the dataset image manager 350. In someembodiments, a volume-commit response from a storage system 120 thatindicates a success status indicates that a volume image has beensuccessfully produced for each and all of one or more volumes of thedataset that are stored to the storage system 120. In some embodiments,a volume-commit response from a storage system 120 that indicates afailure status indicates that a volume image has not been successfullyproduced for one or more volumes of the dataset that are stored to thestorage system 120.

The method 500 determines (at 575) that a volume-commit response hasbeen received from each identified storage system 120 that stores one ormore volumes of the dataset. Each volume-commit response may specify theoperation ID of the overall dataset image operation that the responsepertains to. As each volume-commit response is received from a storagesystem 120, the method 500 may store the value of the volume-commitresponse in the grouping entry 801 for the storage system 120 in thedataset-operation DS 800 corresponding to the received operation ID. Inthe exemplary dataset-operation DS 800 of FIG. 8, a volume-commitresponse 865 data field in each grouping entry 801 indicates whether avolume-commit response indicates a success or failure status.

The method 500 aborts/stops (at 577) the dataset image timeout method600 (described in relation to FIG. 6). As discussed above, the datasetimage timeout method 600 is simultaneously executed for monitoring andimplementing the dataset timeout period that may cause an abort/stoppageof the dataset image method 500. However, if the method 500 hasproceeded to this point, this indicates that the method 500 hasdetermined whether the dataset image is a success or failure before thedataset timeout period expired. As such, the monitoring and enforcing ofthe dataset timeout period by the dataset image timeout method 600 is nolonger needed and can be aborted/stopped.

The method 500 then determines (at 580) whether each and all receivedvolume-commit responses indicate a success status. If so, the method 500determines (at 585) that the overall dataset image operation issuccessful and the dataset image of the dataset is successfullyproduced. As such, the method 500 sends (at 585) a dataset-commitresponse to the application indicating that the dataset image of thedataset has been successfully produced. The dataset-commit response maycomprise a response to the dataset-commit request received (at 565) fromthe application. The dataset-commit response further specifies theoperation ID of the overall dataset image operation that the responsepertains to. The method 500 then ends.

If the method 500 determines (at 580-No) that each and all receivedvolume-commit responses do not indicate a success status, the method 500determines (at 590) that the overall dataset image operation is notsuccessful and the dataset image of the dataset is not successfullyproduced. In these embodiments, if even a single volume-commit responseis received that indicates a failure status, the method 500 determinesthat the overall dataset image operation is not successful. In thismanner, successful production of volume images of each and all volumesof the dataset are needed to determine that the dataset image of thedataset is successfully produced. As such, the method 500 sends (at 590)a dataset-commit response to the application indicating that the datasetimage of the dataset has not been successfully produced. Thedataset-commit response may comprise a response to the dataset-commitrequest received (at 565) from the application. The dataset-commitresponse further specifies the operation ID of the overall dataset imageoperation that the response pertains to.

If the dataset image is not successfully produced, the method 500 theninitiates (at 595) a cleanup/rollback procedure for deleting one or morevolume images of one or more volumes of the dataset. In someembodiments, the cleanup procedure may be used for deleting one or morevolume images that were successfully produced on an identified storagesystem. Since the volume images were produced for an unsuccessful dataimage, the volume images are no longer needed and unnecessarily consumesstorage resources. As such, the cleanup procedure provides automatedremoval of unneeded volume images that were produced for an unsuccessfuldata image. In some embodiments, failed volume images that wereunsuccessfully produced are typically already deleted by the storagesystem 120, and thus typically do not require later removal by thecleanup procedure. In other embodiments, failed volume images are alsodeleted by the cleanup procedure.

In some embodiments, the method 500 initiates (at 595) the cleanupprocedure by sending a volume-cleanup request to the volume imagemanager 250 of each identified storage systems 120 that stores one ormore volumes of the dataset for removing volume images of the one ormore volumes. The method 500 may use the corresponding dataset-operationDS 800 to identify/select each storage system specified in the storagesystem ID 850 data field. The volume-cleanup request may comprise avolume-cleanup application programming interface (API) call from thedataset image manager 350 to the volume image manager 250 of eachidentified storage system 120. Each volume-cleanup request may furtherspecify the operation ID that the request pertains to. Using theoperation ID, the volume image manager 250 of each identified storagesystem 120 may identify the corresponding volume-operation DS anddetermine the volume IDs of those volumes the volume-cleanup requestpertains to (i.e., the volumes of the dataset that are stored to thestorage system 120). In response, the volume image manager 250 of eachidentified storage system 120 will delete one or more volume images ofthe one or more volumes of the dataset that are stored to the storagesystem 120. The method 500 then ends. Note that steps 515-595 of themethod 500 may be repeated for each dataset-start request received froman application.

D. Method for Dataset Image Timeout

FIG. 6 is a flowchart of dataset image timeout method 600 for monitoringand implementing a dataset timeout period for producing a dataset imageof a dataset. The dataset image timeout method 600 may executesimultaneously with the dataset image method 500 of FIG. 5 and may causean abort/stoppage of the dataset image method 600. Steps of method 600may be performed by various hardware and/or software components residingand executing on a computer system 300 and/or storage system 120 thatare configured for performing the method 600. In some embodiments, someor all steps of the method 600 are performed by a dataset image manager350 residing and executing on a computer system 300 (such as a serversystem 110 or storage system 120). The order and number of steps of themethod 600 are for illustrative purposes only and, in other embodiments,a different order and/or number of steps are used.

The method 600 begins when it is initiated (at 605) by the dataset imagemethod 500 for monitoring and implementing a dataset timeout period foran overall dataset image operation for producing a dataset image for adataset (see step 545 of FIG. 5).

The method 600 then determines (at 610) a start time and dataset timeoutperiod for completing the overall dataset image operation. In someembodiments, the method 600 may access the dataset-operation DS 800corresponding to the overall dataset image operation and determine thestart time 815 and dataset timeout period 820. The start time maycomprise an operation start time for producing the dataset image of thedataset. The dataset timeout period may comprise a maximum amount oftime that is allowed/permitted for producing the dataset image of thedataset. The dataset timeout period may be defined by and start from thestart time.

The method 600 then determines (at 615) whether the dataset timeoutperiod has expired. The method 600 may do so by determining whetherthere is no more remaining time in the dataset timeout period. In someembodiments, the method 600 may do so by using the following equation:remaining time=dataset timeout period−(current time−start time). Inthese embodiments, if the method 600 determines (at 615) that theremaining time is equal to zero, the method 600 determines that thedataset timeout period has expired. If the method 600 determines thatthe dataset timeout period has not expired, the method 600 continues atstep 615 to continually monitor the remaining time.

If the method 600 determines (at 615-Yes) the dataset timeout period hasexpired, the method 600 then aborts/stops (at 620) the dataset imagemethod 500 of FIG. 5. Since the dataset timeout period has expired, thedataset image method 500 no longer needs to be executed and may bestopped.

The method 600 then initiates (at 625) a cleanup/rollback procedure fordeleting one or more volume images of one or more volumes of thedataset. The cleanup procedure may be similar to the cleanup procedureof step 595 of the dataset image method 500 and is not discussed indetail here. In some embodiments, the cleanup procedure may be used fordeleting one or more volume images that were successfully produced on anidentified storage system. The method 600 may initiate (at 625) thecleanup procedure by sending a volume-cleanup request to the volumeimage manager 250 of each identified storage systems 120 that stores oneor more volumes of the dataset for removing volume images of the one ormore volumes. The method 600 may use the corresponding dataset-operationDS 800 to identify/select each storage system specified in the storagesystem ID 850 data field. In response, the volume image manager 250 ofeach identified storage system 120 will delete one or more volume imagesof the one or more volumes of the dataset that are stored to the storagesystem 120.

The method 600 then sends (at 630) a dataset-commit response to theapplication indicating that the dataset image of the dataset has notbeen successfully produced. The dataset-commit response may comprise aresponse to the dataset-commit request received from the application.The dataset-commit response further specifies the operation ID of theoverall dataset image operation that the response pertains to. Themethod 600 then ends.

IV. Volume Image Manager for Managing and Producing Volume Images A.Method for Managing and Producing a Volume Image

FIGS. 9A-B is a flowchart of volume image method 900 for managing andproducing one or more volume images of one or more volumes of a dataset.In some embodiments, the dataset comprises a plurality of storageobjects (e.g., volumes) stored on a plurality of different storagesystems 120. Steps of method 900 may be performed by various hardwareand/or software components residing and executing on a storage system120 that are configured for performing the method 900. In someembodiments, some or all steps of the method 900 are performed by avolume image manager 250 residing and executing on a storage system 120that stores one or more volumes of the dataset. The volume image manager250 may operate in conjunction with the storage operating system 230 ofthe storage system 120 to perform some steps of the method 900. Themethod 900 may use various communication messages sent between thevarious components described herein, such as between an application, adataset image manager, and/or a volume image manager. Communicationmessages may be sent between such components, for example, through anetwork, data bus, or the like. The order and number of steps of themethod 900 are for illustrative purposes only and, in other embodiments,a different order and/or number of steps are used.

The method 900 begins when it receives (at 905) a volume-start requestfrom the dataset image manager 350 (see step 550 of FIG. 5). In someembodiments, receiving the volume-start request initiates the startphase of the method 900. The volume-start request may comprise a requestfor suspending one or more volumes of the dataset and begin producingvolume images of one or more volumes of the dataset that are stored tothe storage system 120. The volume-start request may specify all volumesor at least one volume of the dataset (e.g., specify all volume IDs orat least one volume ID of the dataset). In some embodiments, thevolume-start request further specifies an operation ID, a start time,and a dataset timeout period. The operation ID may uniquely identify anoverall dataset image operation for producing a dataset image of thedataset. The start time may comprise the start time for the overalldataset image operation for producing the dataset image of the dataset.The dataset timeout period may comprise a maximum amount of time that isallowed/permitted for the overall dataset image operation to produce thedataset image. The start time and the dataset timeout period may be usedby a volume image timeout method 1000 (described in relation to FIG. 10)to enforce the dataset timeout period.

The method 900 then identifies (at 910) one or more volumes (e.g.,identifies one or more volume IDs) of the dataset that are stored to thestorage system 120, the one or more identified volumes being the volumesthat the volume-start request pertains to. As used herein, an“identified volume” may refer to a volume of the dataset that is storedto the storage system 120 on which the method 900 executes. In someembodiments, the volume-start request specifies all volumes of thedataset, whereby the method 900 identifies (at 910) which particularvolumes of the dataset are stored to its storage system 120. In otherembodiments, the volume-start request specifies only those volumes ofthe dataset that are stored on the storage system 120. In theseembodiments, the method 900 identifies (at 910) all the volumesspecified in the volume-start request.

The method 900 then produces (at 915) a new volume-operation datastructure (DS) 1100 for the operation ID and stores variousdata/information needed for managing and producing the volume images tothe volume-operation DS 1100. Such data may include the operation ID,start time, and dataset timeout period for the overall dataset imageoperation, and volume IDs of the one or more identified volumes. In thismanner, the operation ID may be used by the method 900 to identify anoverall dataset image operation and its corresponding volume-operationDS storing the various data/information for producing volume images forthe overall dataset image operation. As such, only the operation ID maybe needed in communications between the volume image manager 250 and thedataset image manager 350, without needing to continually include otherdata/information (such as start time, dataset timeout period, and/orvolume IDs). The data/information used for managing and producing thevolume images may be organized and stored in the volume-operation DS1100 in various manners using any organizational structure.

FIG. 11 shows a conceptual diagram of an exemplary volume-operation DS1100 in accordance with some embodiments. The volume-operation DS 1100may comprise one or more volume entries 1101 (such as 1101 a, 1101 b,etc.) and a header 1105. The header 1105 may comprise data fields for anoperation ID 1110, start time 1115, and/or dataset timeout period 1120.Each volume entry 1101 represents an identified volume of the datasetthat is stored on the storage system 120. A volume entry 1101representing an identified volume may comprise a plurality of datafields, such as data fields for a volume ID 1155 (e.g., VID16) of theidentified volume, and a plurality of status indicators (such asvolume-start status 1160 and volume-commit status 1165). In theexemplary volume-operation DS 1100 of FIG. 11, the identified volumes ofthe dataset that are stored on the storage system 120 comprise volumesVID16, VID18, and VID19, each identified volume being represented by anentry 1101 in the volume-operation DS 1100.

The method 900 then calls/initiates (at 920) the volume image timeoutmethod 1000. The volume image timeout method 1000 may have access to thevolume-operation DS 1100 and determine the start time and datasettimeout period. Using the start time and dataset timeout period from thevolume-operation DS 1100, the volume image timeout method 1000 mayimplement/enforce the dataset timeout period on the method 900 forproducing the one or more volume images (as discussed in relation toFIG. 10).

The method 900 suspends (at 925) each identified volume of the datasetand begins producing a volume image for each identified volume of thedataset. The method 900 may suspend an identified volume by operating inconjunction with the storage operating system 230 to stop allinput/output (I/O) operations for the volume, which stops accesses(e.g., read or write requests) for the volume. As such, no more writerequests with be performed on the identified volumes after the volumesare suspended so as to prepare the volumes for imaging. After suspendingthe identified volumes, the method 900 initiates procedures forproducing a volume image for each identified volume. An image maycomprise a persistent point in time (PPT) view or image of data of astorage object, such as a volume. An image may provide a read-only copyof a storage object that protects against accidental deletions ormodifications of data of the storage object. As such, an image maycomprise a persistent image of the exact state of the data of thestorage object at a given point in time. An image may comprise a databackup of the storage object that may be used, for example, torestore/recover the data of the storage object after data has beencorrupted, lost, or altered. In some embodiments, the method 900initiates (at 925) procedures for using Snapshot™ technology (providedby NetApp, Inc.) for producing a volume image for each identifiedvolume. In other embodiments, the method 900 initiates (at 925)procedures using other technologies for producing a volume image foreach identified volume.

As each identified volume is suspended and a volume image has beeninitiated, the method 900 updates (at 930) the volume-operation DS 1100to indicate such. The method 900 may do so by locating the volume entry1101 for each identified volume and updating the data field for thevolume-start status 1160 to indicate that the volume is suspended andproducing a volume image has begun. The method 900 then determines (at935) that all identified volumes have been suspended and producing avolume image has begun for all identified volumes. The method 900 may doso by determining that the volume-start status 1160 for the volume entry1101 for each and all identified volumes indicates that the volume issuspended and a volume image has begun.

When the method 900 has successfully completed suspending all volumes ofthe dataset stored on the storage system 120 and initiated producing thevolume images of all volumes of the dataset stored on the storage system120, the method 900 sends (at 940) a volume-start response to thedataset image manager 350 to indicate such. The volume-start responsemay comprise the operation ID of the overall dataset image operationthat the response pertains to.

The method 900 then receives (at 945) a volume-commit request from thedataset image manager 350 (see step 570 of FIG. 5). In some embodiments,receiving the volume-commit request initiates the commit phase of themethod 900. The volume-commit request may comprise a request forcompleting volume images of one or more identified volumes of thedataset that are stored to the storage system 120. In particular, thevolume-commit request may comprise a request for each identified storagesystem 120 to determine and indicate the success or failure of producinga volume image for each and all identified volumes of the dataset thatare stored to the storage system 120. Each volume-commit request mayfurther specify the operation ID that the request pertains to. Using theoperation ID, the method 900 may identify the correspondingvolume-operation DS 1100 and determine the volume IDs of those volumesthe volume-commit request pertains to (i.e., the volumes of the datasetthat are stored to the storage system 120).

When a volume image for an identified volume is successfully produced orfails, the method 900 updates (at 950) the volume-operation DS 1100 toindicate such. The method 900 may do so by locating the volume entry1101 for the identified volume and updating the data field for thevolume-commit status 1165 to indicate whether the volume image for thevolume is a success or a failure.

The method 900 then determines (at 955) whether a commit status for thevolume image for each and all identified volumes has been determined yet(i.e., determined as either a success or a failure). The method 900 maydo so by locating the volume entries 1101 for each and all identifiedvolumes and determining whether each and all volume-commit status datafields 1165 indicate a success or a failure. If the status for volumeimages of each and all identified volumes has not been determined yet(at 955-No), the method 900 continues at step 950.

If the status for volume images of each and all identified volumes hasbeen determined (at 955-Yes), the method 900 aborts/stops (at 957) thevolume image timeout method 1000 (described in relation to FIG. 10). Asdiscussed above, the volume image timeout method 1000 is simultaneouslyexecuted for monitoring and implementing the dataset timeout period thatmay cause an abort/stoppage of the volume image method 900. However, ifthe method 900 has proceeded to this point and reached step 957, thisindicates that the method 900 has completed before the dataset timeoutperiod expired. As such, the monitoring and enforcing of the datasettimeout period by the volume image timeout method 1000 is no longerneeded and can be aborted/stopped.

The method 900 then unsuspends (at 960) all the identified volumes. Themethod 900 may do so by operating in conjunction with the storageoperating system 230 to resume input/output (I/O) operations for allidentified volumes, which allows accesses (e.g., read or write requests)for all identified volumes. Since a volume image has succeeded or failedon each identified volume, the identified volumes no longer need to besuspended to produce volume images. Note that in other embodiments, themethod 900 may unsuspend (at 960) all identified volumes if any volumeimage fails, whereby the method 900 may unsuspend all identified volumeswithout waiting for the status for volume images of all identifiedvolumes.

The method 900 then determines (at 965) whether the commit status forthe volume image for each and all identified volumes is a success. Themethod 900 may do so by locating the volume entries 1101 for each andall identified volumes and determining whether each and allvolume-commit status data fields 1165 indicate a success. If so, themethod 900 sends (at 970) a volume-commit response to the dataset imagemanager 350 indicating a success status. In some embodiments, avolume-commit response from a storage system 120 that indicates asuccess status indicates that a volume image has been successfullyproduced for each and all of one or more volumes of the dataset that arestored to the storage system 120. The volume-commit response may alsospecify the operation ID of the overall dataset image operation that theresponse pertains to. The method 900 then ends.

If the method 900 determines (at 965-No) that the commit status for thevolume image for each and all identified volumes is not a success, themethod 900 then initiates (at 975) a cleanup/rollback procedure fordeleting one or more volume images of one or more identified volumes. Insome embodiments, the cleanup procedure may be used for deleting one ormore volume images that were successfully produced on the storagesystem. As such, the cleanup procedure provides automated removal ofunneeded volume images that were successfully produced. In someembodiments, failed volume images that were unsuccessfully produced aretypically already deleted by the storage system 120, and thus typicallydo not require later removal by the cleanup procedure. In otherembodiments, failed volume images are also deleted by the cleanupprocedure. The method 900 may do so by operating in conjunction with thestorage operating system 230 to delete the volume images of allidentified volumes, the volume images being successful or failed.

The method 900 sends (at 980) a volume-commit response to the datasetimage manager 350 indicating a failure status. In some embodiments, avolume-commit response from a storage system 120 that indicates afailure status indicates that a volume image has not been successfullyproduced for one or more volumes of the dataset that are stored to thestorage system 120. The volume-commit response may also specify theoperation ID of the overall dataset image operation that the responsepertains to. In these embodiments, if even a single volume image fails,producing the volume images of all the identified volumes is consideredfailed, even for any successfully produced volume images. The method 900then ends.

B. Method for Volume Image Timeout

As discussed above, the dataset timeout period may be enforced by thedataset image manager 350 and/or any volume image manager 250 executingon any storage system 120. Each volume image manager 250 may execute avolume image method 900 for producing volume images of volumes of adataset and implement a volume image timeout method 1000 to enforce thedataset timeout period on the particular storage system on which thevolume image manager 250 executes and resides. If the dataset timeoutperiod expires, the volume image manager 250 may cause the volume imagemethod 900 to stop/abort, as well as initiate an image cleanup procedureon the particular storage system.

FIG. 10 is a flowchart of volume image timeout method 1000 formonitoring and implementing a dataset timeout period for producing oneor more volume images of one or more volumes of a dataset. The volumeimage timeout method 1000 may execute simultaneously with the volumeimage method 900 of FIG. 9 and may cause an abort/stoppage of the volumeimage method 1000. Steps of method 1000 may be performed by varioushardware and/or software components residing and executing on a storagesystem 120 that are configured for performing the method 1000. In someembodiments, some or all steps of the method 1000 are performed by avolume image manager 250 residing and executing on a storage system 120that stores one or more volumes of the dataset. The volume image manager250 may operate in conjunction with the storage operating system 230 ofthe storage system 120 to perform some steps of the method 1000. Theorder and number of steps of the method 1000 are for illustrativepurposes only and, in other embodiments, a different order and/or numberof steps are used.

The method 1000 begins when it is initiated (at 1005) by the volumeimage method 900 for monitoring and implementing a timeout period forproducing one or more volume images of an overall dataset imageoperation for producing a dataset image of a dataset (see step 920 ofFIG. 9). The method 1000 then determines (at 1010) a start time and adataset timeout period. In some embodiments, the method 1000 may accessthe volume-operation DS 1100 corresponding to the overall dataset imageoperation and determine the start time 1115 and dataset timeout period1120. The start time may comprise an operation start time for producingthe dataset image of the dataset. The dataset timeout period maycomprise a maximum amount of time that is allowed/permitted forproducing the dataset image of the dataset.

The method 1000 then determines (at 1015) whether a timeout period(dataset timeout period or volume timeout period) has expired. Themethod 1000 may do so by determining whether there is no more remainingtime in the dataset timeout period. If the method 1000 determines (at1015) that the remaining time is equal to zero, the method 1000determines that the timeout period (dataset or volume timeout period)has expired.

In some embodiments, the method 1000 may do so by using the followingequation: remaining time=dataset timeout period−(current time−starttime). In other embodiments, the volume image manager 250 of eachstorage system 120 determines and uses a different timeout period(referred to as a volume timeout period) than the dataset timeoutperiod. The volume timeout period may comprise the dataset timeoutperiod minus a predetermined time amount that accounts for the timeneeded to send the volume-commit response to the dataset image manager350. As such, the volume timeout period may be shorter in time that thedataset timeout period to account for the time needed to send thevolume-commit response to the dataset image manager 350. In theseembodiments, the method 1000 may determine (at 1015) whether the timeoutperiod has expired by determining whether there is no more remainingtime in the volume timeout period by using the following equation:remaining time=volume timeout period−(current time−start time), whereinvolume timeout period=dataset timeout period−predetermined time amount.

In some embodiments, the predetermined time amount may be based onvarious factors, such as the performance capabilities of the storagesystem 120 that executes the volume image manager 250,physical/geographical distance between the storage system 120 thatexecutes the volume image manager 250 and the computer system thatexecutes the dataset image manager 350, etc. As such, the predeterminedtime amount may be different for different volume image managers 250 andstorage systems 120. For example, a first volume image manager executingon a first storage system may have a first predetermined time amount anda first volume timeout period, and a second volume image managerexecuting on a second storage system may have a second predeterminedtime amount and a second volume timeout period, the first and secondpredetermined time amounts being different, and the first and secondvolume timeout periods being different.

If the method 1000 determines (at 1015—No) that the timeout period hasnot expired, the method 1000 continues at step 1015 to continuallymonitor the remaining time. If the method 1000 determines (at 1015—Yes)the timeout period has expired, the method 1000 then unsuspends (at1020) all the identified volumes. The method 1000 may do so by operatingin conjunction with the storage operating system 230 to resumeinput/output (I/O) operations for all identified volumes, which allowsaccesses (e.g., read or write requests) for all identified volumes. Themethod 1000 then aborts/stops (at 1025) the volume image method 900 ofFIG. 9. Since the timeout period has expired, the volume image method900 no longer needs to be executed and may be stopped.

The method 1000 then initiates (at 1030) a cleanup/rollback procedurefor deleting one or more volume images of one or more identified volumesthat are stored to the storage system 120. The cleanup procedure may besimilar to the cleanup procedure of step 975 of the volume image method900 and is not discussed in detail here. In some embodiments, thecleanup procedure may be used for deleting one or more volume imagesthat were successfully produced on the storage system. The method 1000may do so by operating in conjunction with the storage operating system230 to delete the volume images of all identified volumes, the volumeimages being successful or failed. The method 1000 then ends.

C. Method for Cleanup

As discussed above, the dataset image method 500 (at step 595) and/orthe dataset image timeout method 600 (at step 625) may initiate acleanup/rollback procedure if the dataset image is not successfullyproduced within a dataset timeout period. The cleanup procedure may beinitiated on a plurality of storage systems 120 for deleting volumeimages of volumes of the dataset that are stored across the plurality ofstorage systems 120. For example, the cleanup procedure may be initiatedby sending a volume-cleanup request to the volume image manager 250 ofeach storage system 120 that stores one or more volumes of the dataset.

FIG. 12 is a flowchart of cleanup method 1200 for deleting one or morevolume images of one or more volumes of the dataset stored on a storagesystem 120. Steps of method 1200 may be performed by various hardwareand/or software components residing and executing on a storage system120 that are configured for performing the method 1200. In someembodiments, some or all steps of the method 1200 are performed by avolume image manager 250 residing and executing on a storage system 120that stores one or more volumes of the dataset. The volume image manager250 may operate in conjunction with the storage operating system 230 ofthe storage system 120 to perform some steps of the method 1200. Theorder and number of steps of the method 1200 are for illustrativepurposes only and, in other embodiments, a different order and/or numberof steps are used.

The method 1200 begins when it receives (at 1205) a volume-cleanuprequest from the dataset image manager 350. The volume-cleanup requestmay specify the operation ID that the request pertains to. Using theoperation ID, the method 1200 then identifies (at 1210) thecorresponding volume-operation DS 1100 and identifies the volume IDs ofthose volumes the volume-cleanup request pertains to (i.e., the volumesof the dataset that are stored to the storage system 120).

The method 1200 then deletes (at 1215) one or more volume images of theone or more identified volumes of the dataset that are stored to thestorage system 120. In some embodiments, the method 1200 may delete oneor more volume images that were successfully produced on the storagesystem. In other embodiments, failed volume images that wereunsuccessfully produced are typically already deleted by the storagesystem 120, and thus typically do not require later removal by themethod 1200. In other embodiments, failed volume images are also deletedby the method 1200. The method 1200 may do so by operating inconjunction with the storage operating system 230 to delete the volumeimages of all identified volumes, the volume images being successful orfailed. The method 1200 then ends.

As such, even after a volume image manager 250 successfully executes thevolume image method 900 for producing volume images of all identifiedvolumes stored on the storage system within the timeout period, in somesituations, the method 1200 may still delete the successful volumeimages produced on the storage system. This may occur, for example, ifthe timeout period expired before volume images of volumes of thedataset on another storage system were successfully produced and/orvolume images of volumes of the dataset on another storage system hadfailed, thus causing the dataset image method 500 (at step 595) and/orthe dataset image timeout method 600 (at step 625) to initiate thecleanup/rollback procedure on all the identified storage systems. This,in turn, may cause an identified storage system 120 that successfullyproduced all volume images of all identified volumes within the timeoutperiod, to delete all the successful volume images due to the failure ofanother identified storage system.

Various Embodiments

Some embodiments may be conveniently implemented using a conventionalgeneral purpose or a specialized digital computer or microprocessorprogrammed according to the teachings herein, as will be apparent tothose skilled in the computer art. Some embodiments may be implementedby a general purpose computer programmed to perform method or processsteps described herein. Such programming may produce a new machine orspecial purpose computer for performing particular method or processsteps and functions (described herein) pursuant to instructions fromprogram software. Appropriate software coding may be prepared byprogrammers based on the teachings herein, as will be apparent to thoseskilled in the software art. Some embodiments may also be implemented bythe preparation of application-specific integrated circuits or byinterconnecting an appropriate network of conventional componentcircuits, as will be readily apparent to those skilled in the art. Thoseof skill in the art would understand that information may be representedusing any of a variety of different technologies and techniques.

Some embodiments include a computer program product comprising acomputer readable medium (media) having instructions stored thereon/inand, when executed (e.g., by a processor), perform methods, techniques,or embodiments described herein, the computer readable medium comprisinginstructions for performing various steps of the methods, techniques, orembodiments described herein. The computer readable medium may comprisea non-transitory computer readable medium. The computer readable mediummay comprise a storage medium having instructions stored thereon/inwhich may be used to control, or cause, a computer to perform any of theprocesses of an embodiment. The storage medium may include, withoutlimitation, any type of disk including floppy disks, mini disks (MDs),optical disks, DVDs, CD-ROMs, micro-drives, and magneto-optical disks,ROMs, RAMs, EPROMs, EEPROMs, DRAMs, VRAMs, flash memory devices(including flash cards), magnetic or optical cards, nanosystems(including molecular memory ICs), RAID devices, remote datastorage/archive/warehousing, or any other type of media or devicesuitable for storing instructions and/or data thereon/in.

Stored on any one of the computer readable medium (media), someembodiments include software instructions for controlling both thehardware of the general purpose or specialized computer ormicroprocessor, and for enabling the computer or microprocessor tointeract with a human user and/or other mechanism using the results ofan embodiment. Such software may include without limitation devicedrivers, operating systems, and user applications. Ultimately, suchcomputer readable media further includes software instructions forperforming embodiments described herein. Included in the programming(software) of the general-purpose/specialized computer or microprocessorare software modules for implementing some embodiments.

Those of skill would further appreciate that the various illustrativelogical blocks, circuits, applications, modules, algorithms, techniques,processes, or method steps of embodiments described herein may beimplemented as computer electronic hardware, computer software, orcombinations of both. To illustrate this interchangeability of hardwareand software, various illustrative components, blocks, applications,modules, circuits, and steps have been described herein generally interms of their functionality. Whether such functionality is implementedas hardware or software depends upon the particular application anddesign constraints imposed on the overall system. Skilled artisans mayimplement the described functionality in varying ways for eachparticular application, but such implementation decisions should not beinterpreted as causing a departure from the embodiments describedherein.

The various illustrative logical blocks, applications, modules, andcircuits described in connection with the embodiments disclosed hereinmay be implemented or performed with a general-purpose processor, adigital signal processor (DSP), an application-specific integratedcircuit (ASIC), a graphics processing unit (GPU), a field programmablegate array (FPGA) or other programmable logic device, discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described herein. Ageneral-purpose processor may be a microprocessor, but in thealternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

The applications, modules, algorithm, techniques, processes, or methodsdescribed in connection with embodiments disclosed herein may beembodied directly in computer hardware configured to perform theembodiments disclosed herein, in software executed by a processor, or ina combination of the two. In some embodiments, any software application,program, tool, module, or layer described herein may comprise an enginecomprising hardware, software, or a combination of the two configured toperform embodiments described herein. In general, functions of asoftware application, program, tool, module, or layer described hereinmay be embodied directly in hardware, or embodied as software executedby a processor, or embodied as a combination of the two.

A software application, layer, or module may reside in RAM memory, flashmemory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, aremovable disk, a CD-ROM, or any other form of storage medium known inthe art. An exemplary storage medium is coupled to the processor suchthat the processor can read data from, and write data to, the storagemedium. In the alternative, the storage medium may be integral to theprocessor. The processor and the storage medium may reside in an ASIC.The ASIC may reside in a user device. In the alternative, the processorand the storage medium may reside as discrete components in a userdevice.

While the embodiments described herein have been described withreference to numerous specific details, one of ordinary skill in the artwill recognize that the embodiments can be embodied in other specificforms without departing from the spirit of the embodiments. Thus, one ofordinary skill in the art would understand that the embodimentsdescribed herein are not to be limited by the foregoing illustrativedetails, but rather are to be defined by the appended claims.

What is claimed is:
 1. A system, comprising: a dataset image managerengine comprising computer hardware, the dataset image manager engineconfigured for: determining one or more storage systems that store adataset; sending a commit request to a storage system in the one or morestorage systems for producing one or more storage object images of oneor more storage objects of the dataset; receiving a commit response fromthe storage system indicating whether producing the one or more storageobject images is a success or failure; and determining that productionof a dataset image of the dataset is a success based upon the commitresponse.
 2. The system of claim 1, wherein the dataset image managerengine is further configured for: monitoring a timeout period comprisinga maximum amount of time permitted for producing the dataset image. 3.The system of claim 2, wherein the dataset image manager engine isfurther configured for: if the timeout period expires, initiating acleanup procedure for deleting one or more storage object images.
 4. Thesystem of claim 1, wherein the dataset image manager engine is furtherconfigured for, before sending the commit request to the storage system:receiving a start request from an application for producing the datasetimage of the dataset; and upon receiving a start response from thestorage system, sending a resume response to the application.
 5. Thesystem of claim 4, wherein the application is configured for resumingoperations and sending one or more commit requests to the dataset imagemanager engine after receiving the resume response.
 6. The system ofclaim 1, wherein the dataset image manager engine is further configuredfor: producing an operation identifier (ID) for the dataset image, theoperation ID representing an overall dataset image operation forproducing the dataset image for the dataset.
 7. The system of claim 1,wherein the dataset image manager engine is further configured for:performing operations with the one or more storage systems in parallelfor producing at least the dataset image.
 8. A non-transitory computerreadable medium having instructions stored thereon, the non-transitorycomputer readable medium comprising instructions for: determining one ormore storage systems that store a dataset; sending a commit request to astorage system in the one or more storage systems for producing one ormore storage object images of one or more storage objects of thedataset; receiving a commit response from the storage system indicatingwhether producing the one or more storage object images is a success orfailure; and determining that production of a dataset image of thedataset is a failure based upon the commit response.
 9. Thenon-transitory computer readable medium of claim 8, wherein theinstructions further provide for: monitoring a timeout period comprisinga maximum amount of time permitted for producing the dataset image. 10.The non-transitory computer readable medium of claim 8, wherein theinstructions further provide for: initiating a cleanup procedure fordeleting one or more storage object images.
 11. The non-transitorycomputer readable medium of claim 8, wherein the instructions furtherprovide for, before sending the commit request to the storage system:receiving a start request from an application for producing the datasetimage of the dataset; and upon receiving a start response from thestorage system, sending a resume response to the application.
 12. Thenon-transitory computer readable medium of claim 11, wherein theapplication is configured for resuming operations after receiving theresume response.
 13. The non-transitory computer readable medium ofclaim 8, wherein the instructions further provide for: producing anoperation identifier (ID) for the dataset image, the operation IDrepresenting an overall dataset image operation for producing thedataset image for the dataset.
 14. The non-transitory computer readablemedium of claim 8, wherein the instructions further provide for:performing operations with the one or more storage systems in parallelfor producing at least the dataset image.
 15. A method, comprising:determining one or more storage systems that store a dataset; sending acommit request to a storage system in the one or more storage systems;receiving a commit response from the storage system; determining thatproduction of a dataset image of the dataset is a failure based upon thecommit response; and initiating, based upon the failure, a cleanupprocedure for deleting one or more storage object images.
 16. The methodof claim 15, further comprising: monitoring a timeout period comprisinga maximum amount of time permitted for producing the dataset image. 17.The method of claim 15, wherein initiating the cleanup procedurecomprises sending a cleanup request to the storage system.
 18. Themethod of claim 15, further comprising, before sending the commitrequest to the storage system: receiving a start request from anapplication for producing the dataset image of the dataset; and uponreceiving a start response from the storage system, sending a resumeresponse to the application.
 19. The method of claim 18, wherein theapplication is configured for resuming operations after receiving theresume response.
 20. The method of claim 15, further comprising:producing an operation identifier (ID) for the dataset image, theoperation ID representing an overall dataset image operation forproducing the dataset image for the dataset.